Bi-directional project information updates in multi-party bidding

ABSTRACT

In an example embodiment, bid specifications for an ecommerce transaction are transmitted from a party requesting bids to a plurality of bidders. Then a modification to the bid specifications is received from a first bidder of the plurality of bidders along with a bid in accordance with the modified bid specifications. The modified bid specifications may then be transmitted to the plurality of bidders other than the first bidder. Bids in accordance with the modified bid specifications are then received from each of the plurality of bidders other than the first bidder. One of the bids may be selected, and the ecommerce transaction may be consummated based on the selected bid.

CROSS-RELATION TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No.61/861,267 filed Aug. 1, 2013, which is hereby incorporated herein byreference in its entirety.

TECHNICAL FIELD

This application relates generally to data processing. Morespecifically, this application relates to data processing in the contextof social and local commerce.

BACKGROUND

It has long been recognized that allowing consumers to design their ownresidential solar system would be desirable. For solar installers, leadgeneration and sales have become a dominant cost, while for consumersthe process of dealing with sales people and getting multiple quotes ispainful and time-consuming. Both buyer and seller would benefit fromtechnology that would allow a consumer to design their own solar systemsince it could allow consumers to automatically generate a bid, all buteliminating sales costs and effort.

If the size and shape of a roof, its azimuth and inclination angles, andobstructions that shade the roof are known, solar system design isstraightforward, and could potentially be automated. Professional solarinstallers collect this information by going on the roof and takingmeasurements and using instruments to determine shading. It is obviouslyimpractical to expect a consumer to measure their roof and to haveavailable the special instrument that measures shading.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a network diagram depicting a client-server system, withinwhich one example embodiment may be deployed.

FIG. 2 is a block diagram illustrating marketplace and paymentapplications that, in one example embodiment, are provided as part ofapplication server(s) in the networked system.

FIG. 3 is a block diagram illustrating a system for three dimensionalimage mapping in accordance with an example embodiment.

FIG. 4 is a screen capture illustrating a user interface where the usermay enter their address in box 402 in accordance with an exampleembodiment.

FIG. 5 is a screen capture illustrating a user interface where asatellite map has been retrieved and displayed.

FIG. 6 is a screen capture illustrating a user interface where aroofline has been drawn.

FIG. 7 is a screen capture illustrating a user interface where a secondroofline has been drawn.

FIG. 8 is a screen capture illustrating a user interface permitting thedefining of keep out areas.

FIG. 9 is a screen capture illustrating a user interface where a secondview has been presented, in accordance with an example embodiment.

FIG. 10 is a screen capture illustrating a user interface after the userhas aligned the house with the mapping, in accordance with an exampleembodiment.

FIG. 11 is a screen capture illustrating a user interface withcalibration points, in accordance with an example embodiment.

FIG. 12 is a screen capture illustrating a user interface where the userhas selected a particular roofline, in accordance with an exampleembodiment.

FIG. 13 is a screen capture illustrating a user interface where the userhas adjusted all of the rooflines so that the mapping covers the roof ofthe house exactly, in accordance with an example embodiment.

FIG. 14 is a screen capture illustrating a completed mapping inaccordance with an example embodiment.

FIG. 15 is a screen capture illustrating another angle of the completedmapping in accordance with an example embodiment.

FIG. 16 is a screen capture illustrating a solar panel layout onmapping, in accordance with an example embodiment.

FIG. 17 is a screen capture illustrating a specialized user interfacefor solar panel installation mappings in an ecommerce service inaccordance with an example embodiment.

FIG. 18 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 19 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 20 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 21 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 22 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 23 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 24 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 25 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 26 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 27 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 28 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 29 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 30 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 31 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 32 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 33 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 34 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 35 is a screen capture illustrating a heat map on mapping inaccordance with an example embodiment.

FIG. 36 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 37 is a screen capture illustrating the specialized user interfacein accordance with another example embodiment.

FIG. 38 is a flow diagram illustrating a method in accordance with anexample embodiment.

FIG. 39 is a flow diagram illustrating a method in accordance withanother example embodiment.

FIG. 40 is a diagram illustrating an information flow in accordance withan example embodiment.

FIG. 41 is a screen capture illustrating a portion of a questionnaire inaccordance with an example embodiment.

FIG. 42 is a flow diagram illustrating a method in accordance withanother example embodiment.

FIG. 43 is a block diagram illustrating a mobile device, according to anexample embodiment.

FIG. 44 is a block diagram of machine in the example form of a computersystem within which instructions may be executed for causing the machineto perform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

The description that follows includes illustrative systems, methods,techniques, instruction sequences, and computing machine programproducts that embody illustrative embodiments. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide an understanding of various embodiments ofthe inventive subject matter. It will be evident, however, to thoseskilled in the art that embodiments of the inventive subject matter maybe practiced without these specific details. In general, well-knowninstruction instances, protocols, structures, and techniques have notbeen shown in detail.

While many of the concepts in this disclosure may be extended to areasother than solar panel coordination and installation, the presentdisclosure will focus on the aspects relevant to such solar panelembodiments. Nevertheless, this disclosure shall not be deemed to belimited to such embodiments, unless expressly claimed.

In an example embodiment, consumers may be presented with the ability tomap (e.g., obtain the dimensions and angles of) their roofsautomatically, allowing for an environment where users can obtainaccurate bids for solar or other roofing projects (e.g., roofreplacement) without the need for an installer to come and measure theroof in person. One key issue is allowing the consumer to specify with areasonable degree of accuracy the size and shape of their roof, itsinclination angle and azimuth, and how shaded it is.

In an example embodiment, the ability to automatically map roofs orother objects is integrated into an ecommerce service. FIG. 1 is anetwork diagram depicting a client-server system 100, within which oneexample embodiment may be deployed. A networked system 102, in theexample forms of a network-based marketplace or publication system,provides server-side functionality, via a network 104 (e.g., theInternet or a Wide Area Network (WAN)), to one or more clients. FIG. 1illustrates, for example, a web client 106 (e.g., a browser, such as theInternet Explorer browser developed by Microsoft Corporation of Redmond,Wash. State) and a programmatic client 108 executing on respectivedevices 110 and 112.

An Application Program Interface (API) server 114 and a web server 116are coupled to, and provide programmatic and web interfaces respectivelyto, one or more application servers 118. The application servers 118host one or more marketplace applications 120 and payment applications122. The application servers 118 are, in turn, shown to be coupled toone or more database servers 124 that facilitate access to one or moredatabases 126.

The marketplace applications 120 may provide a number of marketplacefunctions and services to users who access the networked system 102. Thepayment applications 122 may likewise provide a number of paymentservices and functions to users. The payment applications 122 may allowusers to accumulate value (e.g., in a commercial currency, such as theU.S. dollar, or a proprietary currency, such as “points”) in accounts,and then later to redeem the accumulated value for products (e.g., goodsor services) that are made available via the marketplace applications120. While the marketplace and payment applications 120 and 122 areshown in FIG. 1 to both form part of the networked system 102, it willbe appreciated that, in alternative embodiments, the paymentapplications 122 may form part of a payment service that is separate anddistinct from the networked system 102.

Further, while the system 100 shown in FIG. 1 employs a client-serverarchitecture, the embodiments are, of course, not limited to such anarchitecture, and could equally well find application in a distributed,or peer-to-peer, architecture system, for example. The variousmarketplace and payment applications 120 and 122 could also beimplemented as standalone software programs, which do not necessarilyhave networking capabilities.

The web client 106 accesses the various marketplace and paymentapplications 120 and 122 via the web interface supported by the webserver 116. Similarly, the programmatic client 108 accesses the variousservices and functions provided by the marketplace and paymentapplications 120 and 122 via the programmatic interface provided by theAPI server 114. The programmatic client 108 may, for example, be aseller application (e.g., the TurboLister application developed by eBayInc., of San Jose, Calif.) to enable sellers to author and managelistings on the networked system 102 in an off-line manner, and toperform batch-mode communications between the programmatic client 108and the networked system 102.

FIG. 1 also illustrates a third party application 128, executing on athird party server machine 130, as having programmatic access to thenetworked system 102 via the programmatic interface provided by the APIserver 114. For example, the third party application 128 may, utilizinginformation retrieved from the networked system 102, support one or morefeatures or functions on a website hosted by the third party. The thirdparty website may, for example, provide one or more promotional,marketplace, or payment functions that are supported by the relevantapplications of the networked system 102.

FIG. 2 is a block diagram illustrating marketplace and paymentapplications 120 and 122 that, in one example embodiment, are providedas part of application server(s) 118 in the networked system 102. Theapplications 120 and 122 may be hosted on dedicated or shared servermachines (not shown) that are communicatively coupled to enablecommunications between server machines. The applications 120 and 122themselves are communicatively coupled (e.g., via appropriateinterfaces) to each other and to various data sources, so as to allowinformation to be passed between the applications 120 and 122 or so asto allow the applications 120 and 122 to share and access common data.The applications 120 and 122 may furthermore access one or moredatabases 126 via the database servers 124.

The networked system 102 may provide a number of publishing, listing,and price-setting mechanisms whereby a seller may list (or publishinformation concerning) goods or services for sale, a buyer can expressinterest in or indicate a desire to purchase such goods or services, anda price can be set for a transaction pertaining to the goods orservices. To this end, the marketplace and payment applications 120 and122 are shown to include at least one publication application 200 andone or more auction applications 202, which support auction-formatlisting and price setting mechanisms (e.g., English, Dutch, Vickrey,Chinese, Double, Reverse auctions, etc.). The various auctionapplications 202 may also provide a number of features in support ofsuch auction-format listings, such as a reserve price feature whereby aseller may specify a reserve price in connection with a listing and aproxy-bidding feature whereby a bidder may invoke automated proxybidding.

A number of fixed-price applications 204 support fixed-price listingformats (e.g., the traditional classified advertisement-type listing ora catalogue listing) and buyout-type listings. Specifically, buyout-typelistings (e.g., including the Buy-It-Now (BIN) technology developed byeBay Inc., of San Jose, Calif.) may be offered in conjunction withauction-format listings, and allow a buyer to purchase goods orservices, which are also being offered for sale via an auction, for afixed-price that is typically higher than the starting price of theauction.

Store applications 206 allow a seller to group listings within a“virtual” store, which may be branded and otherwise personalized by andfor the seller. Such a virtual store may also offer promotions,incentives, and features that are specific and personalized to arelevant seller.

Reputation applications 208 allow users who transact, utilizing thenetworked system 102, to establish, build, and maintain reputations,which may be made available and published to potential trading partners.Consider that where, for example, the networked system 102 supportsperson-to-person trading, users may otherwise have no history or otherreference information whereby the trustworthiness and credibility ofpotential trading partners may be assessed. The reputation applications208 allow a user (for example, through feedback provided by othertransaction partners) to establish a reputation within the networkedsystem 102 over time. Other potential trading partners may thenreference such a reputation for the purposes of assessing credibilityand trustworthiness.

Personalization applications 210 allow users of the networked system 102to personalize various aspects of their interactions with the networkedsystem 102. For example a user may, utilizing an appropriatepersonalization application 210, create a personalized reference page atwhich information regarding transactions to which the user is (or hasbeen) a party may be viewed. Further, a personalization application 210may enable a user to personalize listings and other aspects of theirinteractions with the networked system 102 and other parties.

The networked system 102 may support a number of marketplaces that arecustomized, for example, for specific geographic regions. A version ofthe networked system 102 may be customized for the United Kingdom,whereas another version of the networked system 102 may be customizedfor the United States. Each of these versions may operate as anindependent marketplace or may be customized (or internationalized)presentations of a common underlying marketplace. The networked system102 may accordingly include a number of internationalizationapplications 212 that customize information (and/or the presentation ofinformation by the networked system 102) according to predeterminedcriteria (e.g., geographic, demographic or marketplace criteria). Forexample, the internationalization applications 212 may be used tosupport the customization of information for a number of regionalwebsites that are operated by the networked system 102 and that areaccessible via respective web servers 116.

Navigation of the networked system 102 may be facilitated by one or morenavigation applications 214. For example, a search application (as anexample of a navigation application 214) may enable key word searches oflistings published via the networked system 102. A browse applicationmay allow users to browse various category, catalogue, or inventory datastructures according to which listings may be classified within thenetworked system 102. Various other navigation applications 214 may beprovided to supplement the search and browsing applications.

In order to make listings available via the networked system 102 asvisually informing and attractive as possible, the applications 120 and122 may include one or more imaging applications 216, which users mayutilize to upload images for inclusion within listings. An imagingapplication 216 also operates to incorporate images within viewedlistings. The imaging applications 216 may also support one or morepromotional features, such as image galleries that are presented topotential buyers. For example, sellers may pay an additional fee to havean image included within a gallery of images for promoted items.

Listing creation applications 218 allow sellers to conveniently authorlistings pertaining to goods or services that they wish to transact viathe networked system 102, and listing management applications 220 allowsellers to manage such listings. Specifically, where a particular sellerhas authored and/or published a large number of listings, the managementof such listings may present a challenge. The listing managementapplications 220 provide a number of features (e.g., auto-relisting,inventory level monitors, etc.) to assist the seller in managing suchlistings. One or more post-listing management applications 222 alsoassist sellers with a number of activities that typically occurpost-listing. For example, upon completion of an auction facilitated byone or more auction applications 202, a seller may wish to leavefeedback regarding a particular buyer. To this end, a post-listingmanagement application 222 may provide an interface to one or morereputation applications 208, so as to allow the seller conveniently toprovide feedback regarding multiple buyers to the reputationapplications 208.

Dispute resolution applications 224 provide mechanisms whereby disputesarising between transacting parties may be resolved. For example, thedispute resolution applications 224 may provide guided procedureswhereby the parties are guided through a number of steps in an attemptto settle a dispute. In the event that the dispute cannot be settled viathe guided procedures, the dispute may be escalated to a third partymediator or arbitrator.

A number of fraud prevention applications 226 implement fraud detectionand prevention mechanisms to reduce the occurrence of fraud within thenetworked system 102.

Messaging applications 228 are responsible for the generation anddelivery of messages to users of the networked system 102 (such as, forexample, messages advising users regarding the status of listings at thenetworked system 102 (e.g., providing “outbid” notices to bidders duringan auction process or to provide promotional and merchandisinginformation to users)). Respective messaging applications 228 mayutilize any one of a number of message delivery networks and platformsto deliver messages to users. For example, messaging applications 228may deliver electronic mail (e-mail), instant message (IM), ShortMessage Service (SMS), text, facsimile, or voice (e.g., Voice over IP(VoIP)) messages via the wired (e.g., the Internet), plain old telephoneservice (POTS), or wireless (e.g., mobile, cellular, WiFi, WiMAX)networks 104.

Merchandising applications 230 support various merchandising functionsthat are made available to sellers to enable sellers to increase salesvia the networked system 102. The merchandising applications 230 alsooperate the various merchandising features that may be invoked bysellers, and may monitor and track the success of merchandisingstrategies employed by sellers.

The networked system 102 itself, or one or more parties that transactvia the networked system 102, may operate loyalty programs that aresupported by one or more loyalty/promotions applications 232. Forexample, a buyer may earn loyalty or promotion points for eachtransaction established and/or concluded with a particular seller, andbe offered a reward for which accumulated loyalty points can beredeemed.

FIG. 3 is a block diagram illustrating a system 300 for threedimensional image mapping in accordance with an example embodiment.Here, an image mapping server 302 may retrieve a map from a map database304. A user may then utilize the map, via an image mapping tool 306 on aclient device 308, to interact with the image mapping server 302 toperform various functions that aid in the mapping of three dimensionalobjects on the map.

It should be noted that the image mapping tool 306 may be implemented ina number of different ways. In an example embodiment, the image mappingtool 306 comprises one or more web pages being executed by a browser onthe client device 308. In another example embodiment, the image mappingtool 306 is contained within an application, such as an ecommerceapplication that allows a user to purchaser and/or bid on items andservices, executing on the client device 308. Additionally, in someexample embodiments the image mapping tool 306 actually operates on theimage mapping server 302 and is accessed by the client device 308 over anetwork, such as the Internet.

In an example embodiment, the image mapping tool 306 shows the consumera picture of their house from two or more different views (e.g. astraight down view, and a view that is from the south at a 45 degreeangle, obtained from the map database 304).

The consumer can then trace the sections of their roof on the first viewe.g. by marking corners and other obvious features on the roof. Theconsumer is then shown the tracing that they had made on the first viewoverlaid on the second view. The tracing undergoes a geometrictransformation (i.e. the points are shifted) to represent the differencein angle that the two photographs were taken from.

The consumer then drags the tracing to be on top of their house. Theconsumer is able to drag the points on the tracing so that all points inthe tracing match their corresponding points on this second view.

The tracing on the first view provided the position of each point in twodimensions. Dragging the points to the correct position in the secondview provides the value for the points for that third dimension.

If the first view is from the top, tracing on the first view providesthe X and Y value for each point. Dragging points to the correctposition on the second view provides Z. If the first view is not fromthe top, tracing on the first view provides the X and Y value for eachpoint relative to the angle of the first view and the second viewprovides Z relative to the angle of the first view. These points caneasily be transformed to the X, Y, and Z frame of the surface of theearth by those familiar with the art. Additional views may be shown.These can help determine positions of points that are obscured (by atree for example) on the first two images.

Aerial and satellite photographs are often taken at a nominal 45 degreeangle. These images, unfortunately, typically are not at exactly 45degrees—different portions of the image are at different angles, forexample varying from 43 degrees to 47 degrees.

By allowing the user to drag points in the tracing to match the image inmultiple views, a system of equations may be set up where the actualangle of the photograph is solved for (using multiple equations withmultiple unknowns). This increases the accuracy of the three dimensionalmodel that is created.

Once the positions of all of the points are input, roof angle, azimuth,size and shape can all be determined mathematically. This can beperformed by determining mathematically the azimuth and tilt of theplanes that are defined by the points that were input.

Aerial and satellite photos are commonly available with a nominallystraight-down camera angle, and camera angles that are tilted nominally45 degrees in the North, East, South, and West directions. These are nothowever their true directions, with camera angles often varying widely,e.g. from 35 to 55 degree angles. The true camera angle can be takeninto account in the automatic determination.

In one embodiment, the camera angles are calibrated through an explicitprocess. In this embodiment, three non-collinear points that are at thesame height are identified by the user from two or more camera angles.Because the height from the ground is known to be identical for thesethree points, camera angle can be calculated using the followingprocess:

Three calibration points are identified by the consumer in the top downview (P_(A1), P_(A2), P_(A3)). These three calibration points are movedto the correct location on the roofline by the consumer on the 45 degreeview (P_(B1), P_(B2), P_(B3)). The calibration algorithm iteratesthrough, for example, a ±10 degree span on each of the camera angles(pan, tilt, roll).

Each set of camera angles is applied to P_(A1), P_(A2), P_(A2) andcompared to P_(B1), P_(B2), P_(B3). The angles where the points are theclosest are used for the calibrated camera. In an example embodiment,the camera angles are calculated as follows:

Assuming that there are four non-collinear points (x₁, y₁, z₁) through(x₄, y₄, z₄) viewed through two cameras, A and B, the followingequations apply:For camera A: Projected x _(n)=α*(cos(tilt_(xzA))*Actual x_(n)+sin(tilt_(xzA))*Actual z _(n))For camera A: Projected y _(n)=α*(cos(tilt_(yzA))*Actual y_(n)+sin(tilt_(yzA))*Actual z _(n))For camera B: Projected x _(n)=β*(cos(tilt_(xzB))*Actual x_(n)+sin(tilt_(xzB))*Actual z _(n))For camera B: Projected y _(n)=β*(cos(tilt_(yzB))*Actual y_(n)+sin(tilt_(yzB))*Actual z _(n))

-   -   Where        (x_(n), y_(n), z_(n)) are valid for (x₁, y₁, z₁) through (x₄,        y₄, z₄)        α is the zoom of camera A        β is the zoom of camera B        tilt_(xzA) is the tilt of camera A in the x_(z) direction        tilt_(yzA) is the tilt of camera A in the y_(z) direction        tilt_(xzB) is the tilt of camera B in the x_(z) direction        tilt_(yzB) is the tilt of camera B in the y_(z) direction

If α=1 is normalized, point (x₁, y₁, z₁) is normalized to (0,0,0), andboth tilt_(xzA) and tilt_(yzA) are normalized to (0,0), the followingequations are derived:For camera A: Projected x _(n)=Actual x _(n)For camera A: Projected y _(n)=Actual y _(n)For camera B: Projected x ₁=0For camera B: Projected y ₁=0For camera B: Projected x _(n)=β*(cos(tilt_(xzB))*Projected x _(n) incam A+sin(tilt_(xzB))*Actual z _(n))For camera B: Projected y _(n)=β*(cos(tilt_(yzB))*Projected y _(n) incam A+sin(tilt_(yzB))*Actual z _(n))

-   -   Where        (x_(n), y_(n), z_(n)) are valid for (x₁, y₁, z₁) through (x₄,        y₄, z₄)        β is the zoom of camera B        tilt_(xzB) is the tilt of camera B in the x_(z) direction        relative to camera A        tilt_(yzB) is the tilt of camera B in the y_(z) direction        relative to camera A

Since projected x_(n) and projected y_(n) are provided by the user fromboth camera angles, 6 equations with 6 unknowns are present, which canbe solved for all variables using traditional techniques.

The technique and the mathematics described above can be extended to anindefinite number of cameras at different angles as long as each point'sprojected position is marked by the user in at least two differentcameras of different angles.

In an example embodiment, the user can mark points as certain oruncertain. Points would be marked as uncertain if the object that theyrefer to (for example a particular corner of the roof) is obscured, forexample by a tree. Points that are marked uncertain would not beincluded in the set of equations used to solve for position of the pointand camera angles.

Solar energy collection is affected by obstructions to sunlight, such astrees, chimneys, other buildings, etc. Determining the position of theseobstructions as a 3D model is important for determining potential energyoutput of a given potential location for a solar panel, as it providesthe information necessary to determine which portions of the day thegiven location is shaded. Since energy collection varies by time of day,this is critical information.

In an example embodiment, the user marks the location of theobstructions on each view, just as they did on the roof itself. The sametechniques as were used on the house to determine the 3D model are usedon this new item, the 3D model of which is used to model shading.

In an example embodiment, the user marks a simple shape (such as anellipse) that acts as a bounding area for the obstruction. This isparticularly useful for an obstruction that itself is indistinct, suchas a tree. This bounding shape is changed on each view. In an exampleembodiment this set of data is used to generate 3D data that is used togenerate shading data.

In an example embodiment, the user marks a shape from the straight downview (such as a circle), and then drags a shape (such as a cylinder) tothe height of the obstruction in another view, enclosing the obstructionwith this simple shape. This process acts as a visual method thatreplaces computation of the obstruction at multiple angles. For this tobe possible, the exact angle of each camera must be calculated, asdisclosed earlier in this disclosure.

In an example embodiment the aforementioned set of data is used as aguide as to time of day when a given location would be shaded, i.e. ifthe southwest view shows an obstruction in a given location thislocation will be shaded when the sun is coming from the southwest, sothe energy calculation for that spot would not include the energyproduced during times that the sun is approximately southwest.Additionally in this embodiment, interpolation may be used toapproximate shading for the sun when the sun is in locations that don'thave an image from that direction included in the data set.

Another problem that could exist is lack of accurate calibration data onthe true distance represented by each pixel on the image. In an exampleembodiment, the user is asked to provide the measurement of a singlefeature, such as the width of a driveway. These points and the distancebetween them are marked on the map by the user and are used to calibratethe entire map.

In an example embodiment, the user is asked to mark an element that hasa known dimension, such as the tab to tab distance of a three-tabshingle. This is used to calibrate the image.

After determining the 3D shape of the roof and the obstructions,determination of best position of solar panels may be made.

Once a 3D model of the roof and shading is created, a map of solarenergy potential production may be created using techniques that areknown to those skilled in the art. Likewise the 3D model of the roof maybe used to determine potential positions and orientations of groups ofsolar panels that would physically fit on the roof

In an example embodiment, a cost is generated for each potential solarpanel configuration. This cost may include monetary costs, such as thecost of the solar panels, electronics, mounting hardware, and wiring,but may also include less tangible costs, such as a percentage premiumfor placing solar panels on a side of the building where they are lessaesthetically desirable.

In an example embodiment, the cost value of each potential layout isdivided by the expected energy produced by that layout to generate acost per unit of electricity generated.

In an example embodiment, several optimum solutions are determined andpresented as choices to the user. One optimum solution could be theconfiguration which generates the most energy, without regard to cost.Another optimal solution might be a configuration where the unit cost ofelectricity generated is lowest. Another optimal solution might belowest cost of electricity while placing panels on only a single roofsurface. Another optimal solution might be the smallest solar systemthat is economically viable (i.e. lowers the user's electricity bill bymore than the amount of a monthly lease payment).

In an example embodiment, each section of roof is displayed with arectangular grid overlaid, the size of each rectangle equivalent to thesize of a solar panel. Cells of the grid which don't intersect akeep-out area and are fully bounded by the outline of the section ofroof are displayed in a way that distinguishes them from other gridcells, such as in a different line thickness. A user interface isprovided that allows the user to move the grid on a fine basis, allowingthe user to test solar array position adjustments for how many solarpanels and which positions would be populated on the roof.

In an example embodiment, building code rules are overlaid as keep-outareas. These building code rules may be things like distance from eachedge of the roof that the solar panels cannot be within.

In an example embodiment, these building code rules are crowdsourced,with a table of rules that vary by jurisdiction being kept in a databasethat can be updated by users of sufficient privilege or reputation (suchas solar installers) for use by the entire community.

In an example embodiment, groups of contiguous solar panels aredisplayed for the users, with the user able to select which group orgroups that they wish to include based on a combination of aesthetic andtechnical details as the user sees fit.

In an example embodiment, the above techniques may also be used forother applications that involve extracting a 3D model from a set ofphotographs.

In an example embodiment, the user takes multiple photographs of a roomsuch as a kitchen or closet. They mark off points on the photograph asdisclosed herein, and create a 3D model that can be used to positionvirtual cabinets or built-ins.

The following screen captures illustrate an example embodiment for theabove-described tool.

FIG. 4 is a screen capture illustrating a user interface 400 where theuser may enter their address in box 402 in accordance with an exampleembodiment. The act of entering the address causes the system toretrieve a satellite image of the entered address. FIG. 5 is a screencapture illustrating a user interface 500 where a satellite map has beenretrieved and displayed. The map 502 is displayed, with the exact house504 corresponding to the address centered in the user interface 500. Inthis screen capture, a roofline may be outlined in the tool by the user.

FIG. 6 is a screen capture illustrating a user interface 600 where aroofline 602 has been drawn. Here, the user may draw the roofline 602 byclicking and dragging various points, such as points 604A, 604B, 604C,604D outlining the edge of the roofline, although in some exampleembodiments some or all of this may be performed automatically.

Most houses will contain more than one roofline. In such cases, thesystem may provide additional opportunities for the user to inputadditional rooflines. FIG. 7 is a screen capture illustrating a userinterface 700 where a second roofline 702 has been drawn.

In another example embodiment, the tool permits the user to define keepout areas. These keep out areas define areas of the roofline where solarpanels should not be attached. Examples of such areas are heavily shadedareas (such as areas underneath trees) and areas where elements of thehouse (vent stacks, antennas, satellite dishes, etc.) extend onto theroof.

FIG. 8 is a screen capture illustrating a user interface 800 permittingthe defining of keep out areas. Here, a keep out area 802 has beendefined that is underneath a tree. Additional keep out areas 804A-804Hhave been defined that reflect other obstacles.

It should be noted that while a tool for user definition of such keepout areas is described herein, embodiments are foreseen wherein thesystem automatically defines some or all of the keep-out areas, eitherwith or without user approval of such definitions. For example, some ofthe techniques described herein could be used to automatically detectthe height and orientation of trees adjacent to a house and map shadowpatterns using sun position information over the course of a year todefine a keep out area. Other similar techniques could be used to defineadditional keep-out areas.

Once the user has completed the roofline, including any keep out areas,for a first view, the system may proceed with presenting the user with asecond view for the user to continue the definition of the rooflines inthe second view. As described earlier, this allows the system toautomatically calculate dimensions. FIG. 9 is a screen captureillustrating a user interface 900 where a second view has beenpresented, in accordance with an example embodiment. As can be seen, asatellite photo 902 from a different angle than the first view is nowpresented. Also notably, the mapping 904 the user had provided in thefirst view has been carried over to the second view. As also can be seenin this figure, the user's house 906 is offcenter from the mapping 904.The tool may allow the user to drag the satellite photo 902 to align thehouse 906 with the mapping 904.

FIG. 10 is a screen capture illustrating a user interface 1000 after theuser has aligned the house 906 with the mapping 904, in accordance withan example embodiment. Notably, while the house 906 is now depicted asdirectly underneath the mapping 904, the mapping 904 does not line upperfectly with the rooflines in this satellite photo 902. As such, theuser will need to adjust one or more calibration points to align therooflines exactly with the mapping.

FIG. 11 is a screen capture illustrating a user interface 1100 withcalibration points 1102A-1102C, in accordance with an exampleembodiment. Here, calibration points 1102A-1102C have been highlightedby the tool. These calibration points 1102A-1102C allow the user toclick and drag the mapping 904 to match the roofline exactly. The usermay select which roofline is being modified by clicking on the roofline.FIG. 12 is a screen capture illustrating a user interface 1200 where theuser has selected a particular roofline 1202, in accordance with anexample embodiment. The user may then proceed to adjust the rooflineusing the calibration points 1102B, 1102C. Similar processes may then beperformed on the other rooflines. FIG. 13 is a screen captureillustrating a user interface 1300 where the user has adjusted all ofthe rooflines so that the mapping 904 covers the roof of the house 906exactly, in accordance with an example embodiment.

At this point, enough data has been gathered to calculate theappropriate dimensions and angles using the process described earlier.This results in a 3D mapping that includes dimensions, which can then beused for solar panel installation estimates (or any other purposes).FIG. 14 is a screen capture illustrating a completed mapping 1400 inaccordance with an example embodiment. As can be seen, the mapping 1400includes dimensions, such as dimension 1402, as well as angles, such asangle 1404.

FIG. 15 is a screen capture illustrating another angle of the completedmapping 1400 in accordance with an example embodiment.

At this point, the mapping 1400 can be used for a number of differentpurposes. As described earlier, in some example embodiments the mapping1400 will be used for solar panel installation layouts. These layoutscan be provided with or without user intervention. For example, thesystem may use the mapping 1400 to automatically place an optimum solarpanel layout on the roof. Alternatively, the user can lay out the solarpanels manually. In some embodiments, some combination of the two isused, for example the system may suggest a layout which the user mayedit. FIG. 16 is a screen capture illustrating a solar panel layout onmapping 1400, in accordance with an example embodiment. As can be seen,solar panels, such as panels 1502A and 1502B are laid out on one of thesides of the roof

In an example embodiment, the above-described tool may be integrateddirectly into an ecommerce service. In such a case, a specialized userinterface may be provided. FIG. 17 is a screen capture illustrating aspecialized user interface 1700 for solar panel installation mappings inan ecommerce service in accordance with an example embodiment. Thespecialized user interface 1700 may provide a wizard or other tool thatguides the user through the steps of purchasing a solar system throughthe ecommerce site. As can be seen, there are generally five steps inthis process, including mapping the roof 1702, analyzing the mapping1704, sizing the solar system based on the mapping 1706, getting a pricequote 1708, and checking out 1710 The user interface 1700 at this stageis at the first step, mapping the roof 1702.

FIG. 18 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user isviewing a top view, as indicated by area 1800.

FIG. 19 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hasdrawn one line 1900 of a roof 1902. In some example embodiments, thespecialized user interface 1700 may aid the user in drawing this line1900 by, for example, snapping the line to a detected endpoint of theroof and/or snapping the line to the detected line of the roof, usingimage recognition techniques.

FIG. 20 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hascompleted outlining one roof segment 2000.

FIG. 21 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hasdrawn a line 2100 for a second roof segment 2102.

FIG. 22 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hascompleted outlining another roof segment 2200.

FIG. 23 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hascompleted outlining another roof segment 2300.

FIG. 24 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hasselected roof segment 2300.

FIG. 25 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user canperform various actions on the selected roof segment 2300, such asdeleting or moving the selected roof segment 2300

FIG. 26 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hasselected to view a 3D view by selecting area 2600. This has brought upan additional window 2602 containing an angled three dimensional view ofthe house, here from a southern direction. The additional window 2602 isdisplayed beneath the original top view 2604 to indicate that the viewis from a southern direction.

FIG. 27 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hasaltered the 3D view to a western view. The additional window 2700 isdisplayed to the left of the original top view 2702 to indicate that theview is from a westernly direction.

FIG. 28 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hasaltered the 3D view to an eastern view. The additional window 2800 isdisplayed to the right of the original top view 2802 to indicate thatthe view is from a westernly direction.

FIG. 29 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hasselected the 3D view to be presented alone. As can be seen, the mapping2902 the user had provided in the top view has been carried over to the3D view. As also can be seen in this figure, the user's house 2904 isoffcenter from the mapping 2902. The tool may allow the user to drag thesatellite photo to align the house 2904 with the mapping 2902.

FIG. 30 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hasaligned the house 2904 with the mapping 2902. Notably, while the house2904 is now depicted as directly underneath the mapping 2902, themapping 2902 does not line up perfectly with the rooflines in thissatellite photo. As such, the user will need to adjust one or morecalibration points to align the rooflines exactly with the mapping.

FIG. 31 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here the user hasadjusted all of the rooflines so that the mapping 2902 covers the roofof the house 2904 exactly, in accordance with an example embodiment.

FIG. 32 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here the user hasidentified a keep-out area 3200 in a top view of the house 2904. Thiskeep-out area 3200 corresponds to a tree adjacent to the house 2904.

FIG. 33 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the keep-outarea 3200 identified by the user is depicted in a 3D view. Much likewith the roof mapping 2902, the user is able to adjust the calibrationpoints of the keep-out area 3200 in multiple angled views, allowing thesystem to precisely derive the dimensions of the keep-out area 3200.

FIG. 34 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, additionalkeep-out areas 3300A, 3300B, 3300C, 3300D, 3300E may be marked.

In an example embodiment, the layouts of the solar panels may be basedat least in part on one or more heat maps overlaid on a completedmapping, such as the completed mapping 2902. FIG. 35 is a screen captureillustrating a heat map 3500 on mapping 2902 in accordance with anexample embodiment. The heat map 3500 reflects a prediction of sunactivity over the course of a year. Specifically, the heat map 3500 mayreflect the relative number of hours each portion of the roof mayreceive sun, with the lighter areas such as area 3502 indicating morehours of sun and the darker areas, such as area 3504 indicating fewerhours of sun. In some example embodiments, the heat map 3500 may also bea measure of how direct the sunlight is as opposed to just based onhours. In a sense, the heat map 3500 will reflect the total energyimparted by the sun over the year over the various areas of the roof. Assuch it may take into account not just aggregate hours of sunlight foreach portion but the angle of the sun during those hours. This may beestimated by utilizing astronomical information indicating sun positioninformation over the year for the precise location where the house isfound. It may also take into account any obstructions that may beevident from the satellite images. In such a case, it may be helpful forthe user to provide mappings of not just the roof of the house, but alsomappings of any surrounding potential obstructions, such as trees,telephone poles, walls, neighbor buildings, etc., all of which mayimpact the energy imparted by the sun at the various areas of the roof.The user could, for example, utilize a tool similar to that as describedabove to map not just the dimensions of the roof but of any surroundingobstructions, again by using two more satellite images.

In an example embodiment, historical weather information could also beutilized to help in this estimate. For example, while astronomicalinformation may indicate that a particular area of the roof may get acertain number of hours of direct sun per year, that particular area ofthe roof may only get that sun (according to the astronomicalinformation) during the winter months, and if historical weatherpatterns indicate that most winter days are cloudy in the region, thenthe actual sun received by that area of the roof may be much less thanthe astronomical information implied. Using the historical weatherpatterns allows the system to correct for such issues.

FIG. 36 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hasprogressed to sizing their solar system. A number of package options3600 may be displayed. Here, the user is presented with an idea of theircurrent electrical bill in column 3602, and then presented with a pay asyou go option 3604 and a purchase option 3606, as well as the breakdownof costs and savings from each. These costs and savings may be estimatedbased on predicted bids, as in some example embodiments no bids wouldhave been actually received at this point yet.

FIG. 37 is a screen capture illustrating the specialized user interface1700 in accordance with another example embodiment. Here, the user hasprogressed to obtaining a quote. AS can be seen, a quote 3700 isdisplayed, including a breakdown of costs and savings.

In another example embodiment, the above-described tool may be extendedto images taken from something other than overhead (e.g., satellite)imagery. For example, the front of a user's home could be similarlymapped to aid in bidding for painting or other remodeling projects. Thiscould be performed by, for example, using two different angles of theuser's home taken from street view and applying similar techniques asdescribed above. In such instances, however, it may be necessary to haveinformation about the distance between the camera used for the streetview and the house in order to complete the dimension calculations.

In another example embodiment, the above-described tool may be used toderive dimensions of objects other than homes. Even more generally, theinput images could be any photographs or similar mappings, such asphotographs taken from a user's smartphone, digital camera, or othermobile device. For example, the user may take multiple pictures of apiece of furniture they are thinking about purchasing and use the toolto derive dimension information for the furniture. In such instances theuser may be prompted to, for example, provide information about how faraway they are standing from the object when the pictures are taken.

FIG. 38 is a flow diagram illustrating a method 3800 in accordance withan example embodiment. At operation 3802, a first view of a real-worldobject is displayed from a first angle. At operation 3804, a twodimensional shape is overlaid over the first view. At operation 3806,user interface manipulations of the two dimensional shape are receivedfrom the user, defining the boundaries of a first side of the real-worldobject in the first view. At operation 3808, second view of thereal-world object is displayed from a second angle. At operation 3810,the manipulated two dimensional shape is overlaid over the second view.At operation 3812, additional user interface manipulations of the twodimensional are received from the user, defining the boundaries of thefirst side of the real-world object in the second view. At operation3814, dimensions of the first side of the real-world object are derivedfrom the manipulated two-dimensional object from the second view.

FIG. 39 is a flow diagram illustrating a method 3900 in accordance withanother example embodiment. At operation 3902, a first set of estimatedlocations for calibration points in a roof in a first satellite image isidentified, the first satellite image having a first zoom level and afirst angle relative to ground. At operation 3904, a second set ofestimate locations for the calibration points in the roof in a secondsatellite image is identified, the second satellite image having asecond zoom level and a second angle relative to ground. At operation3906, actual locations for the calibration points are derived using thefirst and second sets of estimated locations, the first and second zoomlevels, and the first and second angles. At operation 3908, dimensioninformation for the roof is calculated based on the derived actuallocations for the calibration points. At operation 3910, a roof mappingis created using the dimension information. At operation 3912, one ormore keep out areas are identified on the roof mapping, the keep outareas identifying areas where a solar panel should not be installed. Atoperation 3914, a layout of a solar panel installation is created usingthe roof mapping and the keep out areas.

In another example embodiment, an online marketplace or e-commerce sitecan be utilized to link potential buyers of solar panels or othersystems can be designed using the above described tools with potentialproviders of such solar panels or systems. An iterative process may beused whereby a potential buyer, who may be unsophisticated, may utilizethe above tools to provide information to the potential providers thatcan be used to make appropriate bids. In the example of a solar panelproject, roof dimensions and angles, as well as keep out areas or otherobstructions can be provided to a plurality of potential providers ofsolar panels. These providers may then utilize this information inpreparing bids that the potential buyer can review. Multiple rounds ofbidding may be utilized so that the potential buyer receives the bestpossible price for the project.

In an example embodiment, the potential providers for the project mayedit one or more parameters of the project prior to providing a bid forthe project. For example, a consumer may have provided a rough solarpanel layout in accordance with instructions provided by the tools. Asolar panel provider, however, may determine that the user'sconfiguration is not optimal, and may correct the configuration prior toproviding a bid. Additionally, these corrected parameters could then beaccepted by the user and transmitted to other potential providers aswell, so that the every potential provider is bidding on the sameproject with the same exact parameters.

This iterative-style bidding process may be extended outside of therealm of solar panels to other ecommerce transactions. It represents avastly different information flow than traditional ecommercetransactions, which currently only involve information flowing from asingle party to another single party. While multibidder transactionsinvolve a single party communicating with many parties, the informationthat is transmitted is only ever transmitted from one party to anotherparty.

FIG. 40 is a diagram illustrating an information flow 4000 in accordancewith an example embodiment. As can be seen, party 4002 may submitinformation, such as specifications 4004, to each bidder 4006, 4008,4010. One of the bidders, here bidder 4006, does not merely just replywith a bid to the specifications, but actually responds with both a bid4012 and revised specifications 4014. The revised specifications 4014are then transmitted from party 4002 to each of the other bidders 4008,4010, who each can make their own bids 4016, 4018 based upon the revisedspecifications 4014, rather than on the original specifications 4004.

In an example embodiment, the original specifications 4004 may be basedon a rough solar panel layout as created by the user, as describedabove, as well as on a questionnaire filled out by the user withadditional details about the user's property or other specifications.FIG. 41 is a screen capture illustrating a portion of a questionnaire4100 in accordance with an example embodiment. As can be seen, the usermay indicate the number of stories 4102 of the house, as well as a roofmaterial type 4104.

Referring back to FIG. 40, the bids from the bidders 4006, 4008, 4010may not just be based on original specifications 4004 or updatedspecifications 4014, but may also be based on information derived fromone or more public databases 4020 and one or more crowdsourced databases4022. Public database 4020 may be, for example, a government countydatabase (or a database that aggregates information from one or moregovernment county databases) that contains information known to thegovernment about the house. This may commonly include information usedin property tax valuation, such as square footage, number of stories,lot size, location, etc. Any discrepancies between this information andthe information provided in the original specifications 4004 may bebrought to the attention of the party 4002. For example, the party 4002may have indicated that the house is two stories while the publicdatabase 4020 shows a single story. The system may then query to theparty 4002 as to which is correct. It is possible that the party 4002committed a typo when entering the number of stories, and thus theoriginal specifications 4004 would need to be corrected. It is alsopossible that the public database 4020 is incorrect, such as if the userhas recently added a second story to their home.

The crowdsourced database 4022 may contain information obtained throughcrowdsourcing, e.g., submitted by other users. These users may either behomeowners themselves, such as neighbors, or may be other bidders 4006,4008, 4010. In the latter case, information that is useful to multiplebidders may be shared between the bidders in order to more efficientlyprocess bids. For example, information about how much permit fees are incertain areas may be shared among bidders 4006, 4008, 4010. This sharingof information may either be voluntary, or may be required as part ofparticipation in the bidding process.

In an example embodiment, a bid database 4024 may be provided that isaccessible to the bidders 4006, 4008, 4010. The bid database 4024 maycontain some or even all the information about the bids from the bidders4006, 4008, 4010. In this way, bidders 4006, 4008, 4010 may be able tosee, for example, how competitive their bid is and subsequently reducetheir price to obtain a better chance of being awarded the job. In someexample embodiments, a system administrator or other entity may set acap/recommended bid for the bids and this information may becommunicated to the bidders 4006, 4008, 4010.

FIG. 42 is a flow diagram illustrating a method 4200 in accordance withanother example embodiment. At operation 4202, bid specifications for anecommerce transaction are transmitted from a party requesting bids to aplurality of bidders. At operation 4204, a modification to the bidspecifications is received from a first bidder of the plurality ofbidders along with a bid in accordance with the modified bidspecifications. At operation 4206, the modified bid specifications aretransmitted to the plurality of bidders other than the first bidder. Atoperation 4208, bids in accordance with the modified bid specificationsare received from each of the plurality of bidders other than the firstbidder. At operation 4210, one of the bids is selected. At operation4212, the ecommerce transaction is consummated based on the selectedbid.

Example Mobile Device

FIG. 43 is a block diagram illustrating a mobile device 4300, accordingto an example embodiment. The mobile device 4300 may include a processor4302. The processor 4302 may be any of a variety of different types ofcommercially available processors suitable for mobile devices (forexample, an XScale architecture microprocessor, a microprocessor withoutinterlocked pipeline stages (MIPS) architecture processor, or anothertype of processor 4302). A memory 4304, such as a random access memory(RAM), a flash memory, or other type of memory, is typically accessibleto the processor 4302. The memory 4304 may be adapted to store anoperating system (OS) 4306, as well as application programs 4308, suchas a mobile location enabled application that may provide LBSs to auser. The processor 4302 may be coupled, either directly or viaappropriate intermediary hardware, to a display 4310 and to one or moreinput/output (I/O) devices 4312, such as a keypad, a touch panel sensor,a microphone, and the like. Similarly, in some embodiments, theprocessor 4302 may be coupled to a transceiver 4314 that interfaces withan antenna 4316. The transceiver 4314 may be configured to both transmitand receive cellular network signals, wireless data signals, or othertypes of signals via the antenna 4316, depending on the nature of themobile device 4300. Further, in some configurations, a GPS receiver 4318may also make use of the antenna 4316 to receive GPS signals.

Modules, Components and Logic

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied (1) on a non-transitorymachine-readable medium or (2) in a transmission signal) orhardware-implemented modules. A hardware-implemented module is atangible unit capable of performing certain operations and may beconfigured or arranged in a certain manner. In example embodiments, oneor more computer systems (e.g., a standalone, client or server computersystem) or one or more processors 4302 may be configured by software(e.g., an application or application portion) as a hardware-implementedmodule that operates to perform certain operations as described herein.

In various embodiments, a hardware-implemented module may be implementedmechanically or electronically. For example, a hardware-implementedmodule may comprise dedicated circuitry or logic that is permanentlyconfigured (e.g., as a special-purpose processor, such as a fieldprogrammable gate array (FPGA) or an application-specific integratedcircuit (ASIC)) to perform certain operations. A hardware-implementedmodule may also comprise programmable logic or circuitry (e.g., asencompassed within a general-purpose processor or other programmableprocessor) that is temporarily configured by software to perform certainoperations. It will be appreciated that the decision to implement ahardware-implemented module mechanically, in dedicated and permanentlyconfigured circuitry, or in temporarily configured circuitry (e.g.,configured by software) may be driven by cost and time considerations.

Accordingly, the term “hardware-implemented module” should be understoodto encompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired) or temporarily ortransitorily configured (e.g., programmed) to operate in a certainmanner and/or to perform certain operations described herein.Considering embodiments in which hardware-implemented modules aretemporarily configured (e.g., programmed), each of thehardware-implemented modules need not be configured or instantiated atany one instance in time. For example, where the hardware-implementedmodules comprise a general-purpose processor configured using software,the general-purpose processor may be configured as respective differenthardware-implemented modules at different times. Software mayaccordingly configure processor 4302, for example, to constitute aparticular hardware-implemented module at one instance of time and toconstitute a different hardware-implemented module at a differentinstance of time.

Hardware-implemented modules can provide information to, and receiveinformation from, other hardware-implemented modules. Accordingly, thedescribed hardware-implemented modules may be regarded as beingcommunicatively coupled. Where multiple of such hardware-implementedmodules exist contemporaneously, communications may be achieved throughsignal transmission (e.g., over appropriate circuits and buses thatconnect the hardware-implemented modules). In embodiments in whichmultiple hardware-implemented modules are configured or instantiated atdifferent times, communications between such hardware-implementedmodules may be achieved, for example, through the storage and retrievalof information in memory structures to which the multiplehardware-implemented modules have access. For example, onehardware-implemented module may perform an operation, and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware-implemented module may then,at a later time, access the memory device to retrieve and process thestored output. Hardware-implemented modules may also initiatecommunications with input or output devices, and can operate on aresource (e.g., a collection of information).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors 4302 that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors 4302 may constitute processor-implementedmodules that operate to perform one or more operations or functions. Themodules referred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods described herein may be at least partiallyprocessor-implemented. For example, at least some of the operations of amethod may be performed by one or more processors 4302 orprocessor-implemented modules. The performance of certain of theoperations may be distributed among the one or more processors 4302, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor 4302 or processors4302 may be located in a single location (e.g., within a homeenvironment, an office environment or as a server farm), while in otherembodiments the processors 4302 may be distributed across a number oflocations.

The one or more processors 4302 may also operate to support performanceof the relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). For example, at least some of theoperations may be performed by a group of computers (as examples ofmachines including processors), these operations being accessible via anetwork (e.g., the Internet) and via one or more appropriate interfaces(e.g., application program interfaces (APIs).)

Electronic Apparatus and System

Example embodiments may be implemented in digital electronic circuitry,or in computer hardware, firmware, software, or in combinations of them.Example embodiments may be implemented using a computer program product,e.g., a computer program tangibly embodied in an information carrier,e.g., in a machine-readable medium for execution by, or to control theoperation of, data processing apparatus, e.g., a programmable processor4302, a computer, or multiple computers.

A computer program can be written in any form of programming language,including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, subroutine,or other unit suitable for use in a computing environment. A computerprogram can be deployed to be executed on one computer or on multiplecomputers at one site or distributed across multiple sites andinterconnected by a communication network.

In example embodiments, operations may be performed by one or moreprogrammable processors 4302 executing a computer program to performfunctions by operating on input data and generating output. Methodoperations can also be performed by, and apparatus of exampleembodiments may be implemented as, special purpose logic circuitry,e.g., a field programmable gate array (FPGA) or an application-specificintegrated circuit (ASIC).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. Inembodiments deploying a programmable computing system, it will beappreciated that that both hardware and software architectures meritconsideration. Specifically, it will be appreciated that the choice ofwhether to implement certain functionality in permanently configuredhardware (e.g., an ASIC), in temporarily configured hardware (e.g., acombination of software and a programmable processor 4302), or acombination of permanently and temporarily configured hardware may be adesign choice. Below are set out hardware (e.g., machine) and softwarearchitectures that may be deployed, in various example embodiments.

Example Machine Architecture and Machine-Readable Medium

FIG. 44 is a block diagram of machine in the example form of a computersystem 4400 within which instructions 4424 may be executed for causingthe machine to perform any one or more of the methodologies discussedherein. In alternative embodiments, the machine operates as a standalonedevice or may be connected (e.g., networked) to other machines. In anetworked deployment, the machine may operate in the capacity of aserver or a client machine in server-client network environment, or as apeer machine in a peer-to-peer (or distributed) network environment. Themachine may be a personal computer (PC), a tablet PC, a set-top box(STB), a personal digital assistant (PDA), a cellular telephone, a webappliance, a network router, switch or bridge, or any machine capable ofexecuting instructions (sequential or otherwise) that specify actions tobe taken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The example computer system 4400 includes a processor 4402 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU), orboth), a main memory 4404 and a static memory 4406, which communicatewith each other via a bus 4408. The computer system 4400 may furtherinclude a video display unit 4410 (e.g., a liquid crystal display (LCD)or a cathode ray tube (CRT)). The computer system 4400 also includes analphanumeric input device 4412 (e.g., a keyboard or a touch-sensitivedisplay screen), a user interface (UI) navigation (e.g., cursor control)device 4414 (e.g., a mouse), a data storage unit 4416, a signalgeneration device 4418 (e.g., a speaker) and a network interface device4420.

Machine-Readable Medium

The data storage unit 4416 includes a computer-readable medium 4422 onwhich is stored one or more sets of data structures and instructions4424 (e.g., software) embodying or utilized by any one or more of themethodologies or functions described herein. The instructions 4424 mayalso reside, completely or at least partially, within the main memory4404 and/or within the processor 4402 during execution thereof by thecomputer system 4400, the main memory 4404 and the processor 4402 alsoconstituting computer-readable media 4422.

While the computer-readable medium 4422 is shown in an exampleembodiment to be a single medium, the term “computer-readable medium”may include a single medium or multiple media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storethe one or more instructions 4424 or data structures. The term“computer-readable medium” shall also be taken to include any tangiblemedium that is capable of storing, encoding or carrying instructions4424 for execution by the machine and that cause the machine to performany one or more of the methodologies of the present disclosure or thatis capable of storing, encoding or carrying data structures utilized byor associated with such instructions 4424. The term “computer-readablemedium” shall accordingly be taken to include, but not be limited to,solid-state memories, and optical and magnetic media. Specific examplesof computer-readable media 4422 include non-volatile memory, includingby way of example semiconductor memory devices, e.g., erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), and flash memory devices;magnetic disks such as internal hard disks and removable disks;magneto-optical disks; and CD-ROM and DVD-ROM disks.

Transmission Medium

The instructions 4424 may further be transmitted or received over acommunications network 4426 using a transmission medium. Theinstructions 4424 may be transmitted using the network interface device4420 and any one of a number of well-known transfer protocols (e.g.,HTTP). Examples of communication networks include a local area network(“LAN”), a wide area network (“WAN”), the Internet, mobile telephonenetworks, plain old telephone (POTS) networks, and wireless datanetworks (e.g., WiFi and WiMax networks). The term “transmission medium”shall be taken to include any intangible medium that is capable ofstoring, encoding or carrying instructions 4424 for execution by themachine, and includes digital or analog communications signals or otherintangible media to facilitate communication of such software.

Although the inventive subject matter has been described with referenceto specific example embodiments, it will be evident that variousmodifications and changes may be made to these embodiments withoutdeparting from the broader spirit and scope of the disclosure.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense. The accompanying drawingsthat form a part hereof, show by way of illustration, and not oflimitation, specific embodiments in which the subject matter may bepracticed. The embodiments illustrated are described in sufficientdetail to enable those skilled in the art to practice the teachingsdisclosed herein. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. ThisDetailed Description, therefore, is not to be taken in a limiting sense,and the scope of various embodiments is defined only by the appendedclaims, along with the full range of equivalents to which such claimsare entitled.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

The invention claimed is:
 1. A system comprising: a bid serverexecutable by a processor and configured to: receive, from a graphicaluser interface, structure specifications for a physical structuregenerated via user interaction with the graphical user interface tocreate and modify one or more overlays over a digital photograph of thephysical structure; transmit structure specifications for the physicalstructure, from a party requesting bids for a service related to thephysical structure, to a plurality of bidders, the structurespecifications not including a price; receive a modification to thestructure specifications from a first bidder of the plurality of biddersalong with a bid including a price in accordance with the modifiedstructure specifications; transmit the modified structure specificationsto the plurality of bidders other than the first bidder; receive bids inaccordance with the modified structure specifications from each of theplurality of bidders other than the first bidder; select one of thebids; and consummate an ecommerce transaction based on the selected bid.2. The system of claim 1, wherein the structure specifications include amapping of a structure relevant to the bids.
 3. The system of claim 2,wherein the structure is a roof of a house and the bids pertain to solarpanel installation.
 4. The system of claim 3, wherein the bidspecifications further include results of a questionnaire sent to theparty requesting bids.
 5. The system of claim 2, wherein the bid serveris further configured to: verify the structure specifications withinformation from a public database.
 6. The system of claim 2, whereinthe bids are created using information from a crowdsource database. 7.The system of claim 6, wherein the bid server is further configured totransmit a maximum bid to each of the plurality of bidders.
 8. Thesystem of claim 1, wherein the structural specifications includeidentifications of areas of a structure that are blocked from sunlight.9. A method comprising: receiving, from a graphical user interface,structure specifications for a physical structure generated via userinteraction with the graphical user interface to create and modify oneor more overlays over a digital photograph of the physical structure;transmitting structure specifications for the physical structure, from aparty requesting bids for a service related to the physical structure,to a plurality of bidders, the structure specifications not including aprice; receiving a modification to the structure specifications from afirst bidder of the plurality of bidders along with a bid including aprice in accordance with the modified structure specifications;transmitting the modified structure specifications to the plurality ofbidders other than the first bidder; receiving bids in accordance withthe modified structure specifications from each of the plurality ofbidders other than the first bidder; selecting one of the bids; andconsummating an ecommerce transaction based on the selected bid.
 10. Themethod of claim 9, wherein the structure specifications include amapping of a structure relevant to the bids.
 11. The method of claim 10,wherein the structure is a roof of a house and the bids pertain to solarpanel installation.
 12. The method of claim 11, wherein the structurespecifications further include results of a questionnaire sent to theparty requesting bids.
 13. The method of claim 9, further comprising:verifying the structure specifications with information from a publicdatabase.
 14. The method of claim 9, wherein the bids are created usinginformation from a crowdsource database.
 15. The method of claim 14,further comprising transmitting a maximum bid to each of the pluralityof bidders.
 16. A non-transitory machine-readable storage medium havingembodied thereon instructions executable by one or more machines toperform operations comprising: receiving, from a graphical userinterface, structure specifications for a physical structure generatedvia user interaction with the graphical user interface to create andmodify one or more overlays over a digital photograph of the physicalstructure; transmitting structure specifications for a physicalstructure, from a party requesting bids for a service related to thephysical structure, to a plurality of bidders, the structurespecifications not including a price; receiving a modification to thestructure specifications from a first bidder of the plurality of biddersalong with a bid including a price in accordance with the modifiedstructure specifications; transmitting the modified structurespecifications to the plurality of bidders other than the first bidder;receiving bids in accordance with the modified structure specificationsfrom each of the plurality of bidders other than the first bidder;selecting one of the bids; and consummating an ecommerce transactionbased on the selected bid.
 17. The non-transitory machine-readablestorage medium of claim 16, wherein the structure specifications includea mapping of a structure relevant to the bids.
 18. The non-transitorymachine-readable storage medium of claim 17, wherein the structure is aroof of a house and the bids pertain to solar panel installation. 19.The non-transitory machine-readable storage medium of claim 18, whereinthe structure specifications further include results of a questionnairesent to the party requesting bids.
 20. The non-transitorymachine-readable storage medium of claim 16, further comprising:verifying the structure specifications with information from a publicdatabase.
 21. The non-transitory machine-readable storage medium ofclaim 16, further comprising transmitting a maximum bid to each of theplurality of bidders.